fix(rehearsal): configurable grant lifetimes; document caching and custom-domain rationale - #9
Merged
Merged
Conversation
…stom-domain rationale The grant scripts hardcoded --credential-ttl 1h --minimum-upload-window 15m, which fits the tiny circuit but not a production-sized turn: a K=21 contribution can spend the better part of an hour computing before its upload begins, so the grant expires mid-turn and the scripts have to be bypassed. Make both values env-configurable (PARTICIPANT_GRANT_TTL, PARTICIPANT_GRANT_MIN_UPLOAD_WINDOW, EVIDENCE_GRANT_TTL, EVIDENCE_GRANT_MIN_UPLOAD_WINDOW) with the previous values as defaults, and document them in the machine-1 env example. STORAGE.md additions from the 2026-08-20 measurements: - spell out the stale-pointer failure mode behind the state/* no-cache rule, give the write-read-overwrite-read probe procedure, and record that both guided setups are uncached by construction (CloudFront CachingDisabled; r2.dev does not cache) so blob/* caching is a pure optimization that requires re-running the probe; - clarify that the production custom domain is an availability and longevity requirement, not an integrity one, and that switching to it changes the caching surface.
mellowcroc
force-pushed
the
fix/grant-ttl-and-storage-docs
branch
from
August 20, 2026 17:15
536525d to
1daf628
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two follow-ups from running the flow at production size (2026-08-20 Relay-driven K=21 first-head test):
1. Grant lifetimes are env-configurable. The grant scripts hardcoded
--credential-ttl 1h --minimum-upload-window 15m— fine for the tiny circuit, but a K=21 contribution can spend most of an hour computing before its upload begins, so the grant expired mid-turn and the scripts had to be bypassed with a directrelay coordinator grant. Both values are now env-configurable (PARTICIPANT_GRANT_TTL,PARTICIPANT_GRANT_MIN_UPLOAD_WINDOW,EVIDENCE_GRANT_TTL,EVIDENCE_GRANT_MIN_UPLOAD_WINDOW) with the previous values as defaults, documented in the machine-1.envexample.2. STORAGE.md: measured caching facts + custom-domain rationale.
state/*no-cache rule (participants stuck on "not your turn", witnesses missing the closure window, no error anywhere) and gives the 5-minute write→read→overwrite→read probe to verify freshness per origin.CachingDisabled;r2.devdoes not cache at all) — soblob/*caching is a pure optimization that requires re-running the probe.